Blueprints

Blueprints are comprised of a series of actions applied to data, and are created in the Architect. These blueprints can be deployed according to a schedule, to apply the actions to source data at a scheduled time. Selecting a blueprint file (with a .mgd file extension) to deploy will open a configuration dialog if the blueprint is valid.

Note: A blueprint is valid for scheduled deployment if it contains only historical sources, and no real-time sources.

  • Continue with configuration, and click [OK] when complete to add the AO to the list of scheduled Action Objects.

Example: configuring the Action Object to execute

Action Object name

This is the name of the selected blueprint for deployment, according to a defined schedule.

  • Default = the name of the blueprint.
  • A blueprint can be selected more than once, with a different source selected each time.

    Properties of a valid name:

    • Name must be unique to the Action Object Server

    • Character cases are ignored

    • Special characters are allowed

    • Maximum permitted length: 450 characters

Data source window(s)

Source:

  • In the list view, all valid blueprint sources are listed.

    • Valid sources are all historical sources, that are configured to use a data window option in the blueprint.

    • Historical sources that were not configured in the blueprint to use a data window will not be listed here for deployment, even though the blueprint is still valid.

    • Any real-time sources will show an error message if selected, and cannot be deployed.

  • For each source, a data window size and an offset time must be set.

    • To configure a source, select the source in the list by clicking on it.

    • Below the list view, the window size and offset text boxes become active. As you set the values for each of these, the values will be checked for validity. If valid, the values will automatically update in the list view.

Window size

This is the size of the window for data retrieval from the source.

  1. When a source is selected, below the list view, the window size and offset text boxes become active.

  2. As you set the values for each of these, the values will be checked for validity. If valid, the values will automatically update in the list view.

  3. Define the window size as d hh:mm:ss or the total number of minutes.

Offset

The time between the end of the data window and the scheduled time for executing the Action Object.

Properties of a valid offset:

  • must be an integer

  • must be greater than or equal to 0

  1. As you define the offset size in the offset text box, valid values will automatically update in the list view.

  2. The offset is shown as hh:mm:ss.

Action Object schedule

Define when the Action Object will be executed. This can occur either once, or periodically.

  • Set the scheduled start date and time, either manually or by using the available calendar.

  • The time to be set is LOCAL time.

  • Schedule the deployment period in h:mm:ss

Example: Scheduling an Action Object to execute

If the settings are defined as:

  • window size = 1 hour

  • offset  = 30 minutes, and

  • scheduled time of deployment is 13:00:00

then the following will happen on deployment:

  • data will be retrieved over 1 hour, from 11:30:00 to 12:30:00

  • a 30 minute offset will last from 12:30:00 to 13:00:00

  • the Action Object deployment will occur at 13:00:00


Related topics:

  

CSense 2023- Last updated: June 24,2025